Computer-based systems configured to manage continuous integration/continuous delivery programming pipelines with their associated datapoints and methods of use thereof

ABSTRACT

Systems and methods associated with performing checkpoint and build processing associated with a continuous integration/continuous deployment (CI/CD) pipeline. In one embodiment, an exemplary method may include identifying an outside dependence for a new cloud process to be integrated into a CI/CD build of a CI/CD pipeline, determining on a periodic or ongoing basis whether a current status of the outside dependence identifies it as incomplete such that a new cloud process would not perform as desired until the dependence is complete, preventing the new cloud process from being integrated into the CI/CD build until the current status indicates that the outside dependence is complete, and integrating the new cloud process into the CI/CD build when the current status indicates that the outside dependence is complete.

CROSS-REFERENCE TO RELATED APPLICATION(S) INFORMATION

This is a continuation of U.S. application Ser. No. 16/588,263, filedSep. 30, 2019, now U.S. Pat. No. 10,728,364, which are incorporatedherein by reference in entirety.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document may contain materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever. The following notice applies to the software and dataas described below and in drawings that form a part of this document:Copyright, Capital One Services, LLC., All Rights Reserved.

FIELD OF TECHNOLOGY

The present disclosure generally relates to an improved computer-basedplatform or system, improved computing devices and/or improved computingmethods configured for one or more novel technological applicationsinvolving checkpoint and build processing associated with cloud-basedsoftware applications being executed as part of a continuousintegration/continuous delivery (CI/CD) pipeline.

BACKGROUND OF TECHNOLOGY

A computer network platform or system may include a group of computers(e.g., clients, servers, smart routers, etc.) and other computinghardware devices that are linked together through one or morecommunication channels to facilitate communication, software managementand/or coordinating separate processes, such as with execution incloud-based computing environments.

Software developers often use continuous integration/continuous delivery(CI/CD) pipelines to build applications or functionality for desiredenvironments by requisitioning and coordinating separate cloudprocesses. At present, managing separate cloud processes, such asaligning checkpoints, statuses and completion of tasks during build, canbe limited by numerous restraints such as, without limitation,inoperability of distinct software packages/routines, etc. There isoften no satisfactory mechanism for managing and/or aligning variouscloud processes based on the completion of each service. Further, suchdrawbacks can be especially problematic when only a limited subset ofcloud services are available, and/or when additional limitations areplaced on which application mechanisms are available, e.g., due tosecurity and/or privacy considerations or the like.

SUMMARY OF DESCRIBED SUBJECT MATTER

In some embodiments, the present disclosure provides various exemplarytechnically improved computer-implemented methods for performingcheckpoint and build processing regarding software applications involvedwith a CI/CD pipeline, including a method having steps such as:

receiving, by at least one computer processor, an indication of at leastone first new cloud process to be integrated into a continuousintegration/continuous deployment (CI/CD) build of a CI/CD pipeline;

identifying, by the at least one computer processor, at least oneoutside dependence for the at least one first new cloud process;

wherein the at least one outside dependence comprises input data that isgenerated outside of one or both of: the at least one first new cloudprocess, and at least one computing activity performed outside of the atleast one first new cloud process;

querying, by the at least one computer processor, an updatablecentralized log to determine a current status of the at least oneoutside dependence;

wherein the updatable centralized log is configured to obtain, inreal-time, outside dependencies associated with the CI/CD build of theCI/CD pipeline;

determining, by the at least one computer processor, on a periodic orongoing basis, whether the current status of the at least one outsidedependence identifies that the at least one outside dependence isincomplete so that the at least one first new cloud process would notperform as desired until the at least one outside dependence iscomplete;

wherein the current status is determined by one or both of:

-   -   (i) tracking datapoints transmitted from one or more third-party        platforms associated with the outside dependence; and    -   (ii) tracking the datapoints existent on the one or more        third-party platforms;

preventing, by the at least one computer processor, the at least onefirst new cloud process to be integrated into the CI/CD build of theCI/CD pipeline until the current status of the at least one outsidedependence identifies that the at least one outside dependence iscomplete; and

integrating, by the at least one computer processor, the at least onefirst new cloud process into the CI/CD build of the CI/CD pipeline whenthe current status of the at least one outside dependence identifiesthat the at least one outside dependence is complete.

In some embodiments, the present disclosure also provides exemplarytechnically improved computer-based systems and computer-readable media,including media implemented with and/or involving one or more softwareapplications, whether resident on computer devices or platforms,provided for download via a server and/or executed in connection with atleast one network such as via a web application, that include orinvolves features, functionality, computing components and/or stepsconsistent with any aspects set forth herein.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the present disclosure can be further explainedwith reference to the attached drawings, wherein like structures arereferred to by like numerals throughout the several views. The drawingsshown are not necessarily to scale, with emphasis instead generallybeing placed upon illustrating the principles of the present disclosure.Therefore, specific structural and functional details disclosed hereinare not to be interpreted as limiting, but merely as a representativebasis for teaching one skilled in the art to variously employ one ormore illustrative embodiments.

FIG. 1 is a block diagram depicting an exemplary computer-based systemand/or platform that may involve features of checkpoint and buildprocessing, in accordance with certain embodiments of the presentdisclosure.

FIG. 2 is a block diagram depicting another exemplary computer-basedsystem and/or platform that may involve features of checkpoint and buildprocessing, in accordance with certain embodiments of the presentdisclosure.

FIGS. 3 and 4 are diagrams illustrating two exemplary implementations ofcloud computing architecture/aspects with respect to which the disclosedtechnology may be specifically configured to operate, in accordance withcertain embodiments of the present disclosure.

FIG. 5 is a high-level block diagram illustrating some exemplaryfeatures related to performing checkpoint and build processingassociated with a CI/CD pipeline, consistent with exemplary aspects ofcertain embodiments of the present disclosure.

FIG. 6 is a flowchart illustrating one exemplary process related toperforming checkpoint and build processing associated with a CI/CDpipeline, consistent with exemplary aspects of certain embodiments ofthe present disclosure.

FIG. 7 is a block diagram of an exemplary system and/or platform thatmay involve features of checkpoint and build processing, consistent withexemplary aspects of certain embodiments of the present disclosure.

DETAILED DESCRIPTION

Various detailed embodiments of the present disclosure, taken inconjunction with the accompanying figures, are disclosed herein;however, it is to be understood that the disclosed embodiments aremerely illustrative. In addition, each of the examples given inconnection with the various embodiments of the present disclosure isintended to be illustrative, and not restrictive.

Throughout the specification, the following terms take the meaningsexplicitly associated herein, unless the context clearly dictatesotherwise. The phrases “in one embodiment” and “in some embodiments” asused herein do not necessarily refer to the same embodiment(s), thoughit may. Furthermore, the phrases “in another embodiment” and “in someother embodiments” as used herein do not necessarily refer to adifferent embodiment, although it may. Thus, as described below, variousembodiments may be readily combined, without departing from the scope orspirit of the present disclosure.

Systems and methods associated with performing checkpoint and buildprocessing of software applications, such as those assembled via cloudprocesses and associated with a CI/CD pipeline, are disclosed. Accordingto the disclosed technology, solutions herein may involve managing CI/CDbuild processes including tracking of completion statuses amongdifferent separate cloud processes, and taking various actions based ondatapoints regarding and/or completion of the underlying tasks andsubtasks. In some embodiments, subsequent steps of a CI/CD pipelineexecution may be managed and/or curtailed based on reporting and statusinformation being generated and handled. Further, systems and methodsherein may be especially applicable and specially designed for use inrestrictive data environments, such as customer data environments thatmay be subject to data protection and/or data privacy rules orgovernances, or are otherwise limited only to services and activitiesapproved for use therein. The disclosed embodiments may execute a methodor pattern of checkpoint and build processing, including use of a toolor log external to the CI/CD pipeline that records and reportsdatapoints, which is configured to operate in conjunction with, andwithout violating, safeguards in place for particular data environments,such as environments that are especially strict in terms of security andbest practices for protecting customer data.

In some embodiments, for example, execution and completion of dependentprocesses being spun up and executed from a CI/CD build may be alignedin connection with datapoints processed and reported by the externaltool or log. Methods herein may originate from within a CI/CD pipelineexecution though may track progress or completion of each processseparately, wherein further execution of the pipeline build processesmay be based on such tracking. Further, the present methods utilizeother unique features, and involving the alignment of several differentsystems, to achieve objectives such as efficient completion of a CI/CDpipeline execution build. In some aspects, status, such as completionstatus, of the various separate processes may be captured, reported andprocessed such that execution of downstream steps in a CI/CD pipelineexecution may be aligned and implemented based on those statuses.

FIG. 1 is a block diagram depicting an exemplary computer-based systemand/or platform that may involve features of checkpoint and buildprocessing, in accordance with certain embodiments of the presentdisclosure. It is noted, however, that not all of the illustratedcomponents may be required to practice one or more embodiments, andvariations in the arrangement and type of the components may be madewithout departing from the spirit or scope of various embodiments of thepresent disclosure. In some embodiments, the exemplary inventivecomputing devices and/or the exemplary inventive computing components ofthe exemplary computer-based system/platform may be configured to managea large number of processes and/or concurrent interactions, as detailedherein. In some embodiments, the exemplary computer-basedsystem/platform may be based on a scalable computer and/or networkarchitecture that incorporates various strategies for assessing thedata, caching, searching, and/or database connection pooling. An exampleof the scalable architecture is an architecture that is capable ofoperating multiple servers.

In some embodiments, referring to FIG. 1, members 102-104 (e.g.,clients) of the exemplary computer-based system/platform may includevirtually any computing device capable of receiving and sending amessage over a network (e.g., organization intranet, cloud network,etc.), such as network 105, to and from another computing device, suchas servers 106 and 107, each other, and the like. In some embodiments,the member devices 102-104 may be personal computers, multiprocessorsystems, microprocessor-based or programmable consumer electronics,network PCs, and the like, with some examples set forth in more detail,below, in connection with FIG. 7.

In some embodiments, the exemplary network 105 may provide networkaccess, data transport and/or other services to any computing devicecoupled to it. In some embodiments, the exemplary network 105 mayinclude and implement architecture for performing cloud-based computingand/or include or involve at least one specialized network architecture,as described in more detail below. In some embodiments, the exemplaryserver 106 or the exemplary server 107 may be a web or cloud server (ora series of servers) running a network operating system.

In some embodiments and, optionally, in combination of any embodimentdescribed above or below, for example, one or more exemplary computingmember devices 102-104, the exemplary server 106, and/or the exemplaryserver 107 may include a specifically programmed software module thatmay be configured to send, process, and receive information using ascripting language, a remote procedure call, an email, a tweet, ShortMessage Service (SMS), Multimedia Message Service (MMS), instantmessaging (IM), internet relay chat (IRC), mIRC, Jabber, an applicationprogramming interface, Simple Object Access Protocol (SOAP) methods,Common Object Request Broker Architecture (CORBA), HTTP (HypertextTransfer Protocol), REST (Representational State Transfer), or anycombination thereof.

It is to be understood that the configuration and boundaries of thefunctional building blocks of system 100 have been defined herein forthe convenience of the description. Alternative boundaries can bedefined so long as the specified functions and relationships thereof areappropriately performed. Alternatives (including equivalents,extensions, variations, deviations, etc., of those described herein)will be apparent to persons skilled in the relevant art(s) based on theteachings contained herein. Such alternatives fall within the scope andspirit of the disclosed embodiments.

FIG. 2 is a block diagram depicting another exemplary computer-basedsystem and/or platform that may involve features of checkpoint and buildprocessing, in accordance with certain embodiments of the presentdisclosure. It is noted that not all of these components may be requiredto practice one or more embodiments, and variations in the arrangementand type of the components may be made without departing from the spiritor scope of various embodiments of the present disclosure. In someembodiments, the member computing devices 202 a, 202 b through 202 nshown each at least includes a memory 208, such as a random-accessmemory (RAM) and/or a computer-readable medium, which may be coupled toa processor 210. In some embodiments, the processor 210 may executecomputer-executable program instructions stored in memory 208.

Referring to FIG. 2, various computer-executable instructions may beexecuted in connection with providing a continuous integration,continuous delivery (CI/CD) platform or pipeline 218 that the client 202a may utilize, e.g., to initiate, track and/or coordinate various cloudprocesses or services, such as those associated with a software orapplication build. Such CI/CD platform or pipeline 218 may be specificto a single application and executed using a CI/CD tool, like Jenkins.Further, in some implementations, client (e.g. 202 a) may be associatedwith a financial service provider (FSP) entity that provides, maintains,manages, or otherwise offers financial services. For example, thefinancial service entity may be a bank, credit card issuer, or any othertype of financial service entity that generates, provides, manages,and/or maintains financial service accounts for one or more customers.Financial service accounts may include, for example, credit cardaccounts, loan accounts, checking accounts, savings accounts, reward orloyalty program accounts, and/or any other type of financial serviceaccount known to those skilled in the art. In such instances, client 202a may be comprised of a plurality of servers including one or moreservers or computer systems that implement the CI/CD platform orpipeline, which may be resident on other servers.

As shown in FIG. 2, exemplary clients 202 may be also coupled to one ormore networks 105 as well as to one or more cloud computing environments224, which may contain the various cloud processes and cloud servicesthat the CI/CD pipeline 218 initiates, instructs and coordinates. Asalso shown in FIG. 2, exemplary cloud computing environment 224 mayinclude and/or involve one or more servers 204, 213 and/or cloudcomponents 225, which are shown grouped together in the drawing for sakeof illustration, though may be distributed in various ways as known inthe art. The various different servers 204, 213 may execute the separatecloud processes coordinated via embodiments herein, and each may containprocessors 205, 214, memory 217, 216 and associated network or cloudengines. Cloud components 225 may include one or more cloud servicessuch as software applications (e.g., queue, etc.), one or more cloudplatforms (e.g., a Web front-end, etc.), cloud infrastructure (e.g.,servers 204, 213, virtual machines, etc.), and/or cloud storage (e.g.,cloud databases, network databases 207, 215, etc.), which are furtherdiscussed in connection with FIGS. 3 and 7.

In some embodiments, one or more databases, such as exemplary databases207 and 215, may be any type of database, including a database managedby a database management system (DBMS). In some embodiments, anexemplary DBMS-managed database may be specifically programmed as anengine that controls organization, storage, management, and/or retrievalof data in the respective database. In some embodiments, the exemplaryDBMS-managed database may be specifically programmed to provide theability to query, backup and replicate, enforce rules, provide security,compute, perform change and access logging, and/or automateoptimization. In some embodiments, the exemplary DBMS-managed databasemay be chosen from Oracle database, IBM DB2, Adaptive Server Enterprise,FileMaker, Microsoft Access, Microsoft SQL Server, MySQL, PostgreSQL,and a NoSQL implementation. In some embodiments, the exemplaryDBMS-managed database may be specifically programmed to define eachrespective schema of each database in the exemplary DBMS, according to aparticular database model of the present disclosure which may include ahierarchical model, network model, relational model, object model, orsome other suitable organization that may result in one or moreapplicable data structures that may include fields, records, files,and/or objects. In some embodiments, the exemplary DBMS-managed databasemay be specifically programmed to include metadata about the data thatis stored.

In FIGS. 1 and 2, while only one or several of the various systemcomponents are shown, it will be understood that these platforms 100,200 may include more or fewer of any of these components, than depicted.More generally, the components and arrangement of the componentsincluded in these platforms 100, 200 may vary. Thus, platforms 100, 200may include other components that perform or assist in the performanceof one or more processes consistent with the disclosed embodiments.Another exemplary, generalized computing platform is further shown anddescribed below in connection with FIG. 7.

As shown in FIGS. 2 and 3, various embodiments of the disclosedtechnology may include and/or involve one or more cloud components 225,which are shown grouped together in the drawing for sake ofillustration, though may be distributed in various ways as known in theart. Cloud components 225 may include one or more cloud services such assoftware applications (e.g., queue, etc.), one or more cloud platforms(e.g., a Web front-end, etc.), cloud infrastructure (e.g., virtualmachines, etc.), and/or cloud storage (e.g., cloud databases, etc.).

According to some embodiments shown by way of one example in FIG. 4, theexemplary inventive computer-based systems/platforms, the exemplaryinventive computer-based devices, components and media, and/or theexemplary inventive computer-implemented methods of the presentdisclosure may be specifically configured to operate in or with cloudcomputing/architecture such as, but not limiting to: infrastructure aservice (IaaS) 410, platform as a service (PaaS) 408, and/or software asa service (SaaS) 406. In some embodiments, such cloud architecture 406,408, 410 may be utilized in connection with web browser and/or othernetwork aspects, shown at 404, to provide implementations herein.

FIG. 5 is a high-level block diagram illustrating some exemplaryfeatures related to performing checkpoint and build processingassociated with a CI/CD pipeline, consistent with exemplary aspects ofcertain embodiments of the present disclosure. Referring to FIG. 5, anexemplary CI/CD pipeline process begins by initiating the pipeline, at502, which begins the CI/CD build and starts building the code and thedeployment process. The build includes commencing a primary process and,eventually, the need to invoke at least one secondary process, such as aperformance test, at which time the CI/CD build process is paused, at504. At this point, the CI/CD build will wait and monitor the secondaryprocess, which is being run, e.g., on a third-party platform. Thesecondary process is then executed, as shown at 506. Upon completion ofthe secondary process, a notification regarding completion (orintermediate status) is transmitted to a datapoint, at 508, which is onthe third-party platform. At 508, the notification or datapoint isrecorded and a sub-process is initiated to report the status informationto the CI/CD build. A sub-process for performing such datapointreporting is shown, at 510, by way of illustration. This reportingsub-process 510 may include periodic monitoring of the third-partyplatform, by the CI/CD pipeline, to see if the datapoint has beenrecorded. The CI/CD pipeline may perform such monitoring until thesubject datapoint is recorded, and, further, the pipeline may also beconfigured with a timeout period and/or other wait instructions thatwill trigger an error in the build process if a timeout period haselapsed or other criteria is met. Once the secondary process is finishedand posting of the datapoint has been verified to confirm completion,the CI/CD build may be unblocked and the pipeline may continue with therest of the deployment. In some embodiments, for example, the CI/CDpipeline may use or assess the results of the secondary process (e.g.,the results of performance tests, etc.) and proceed with the build.

According to certain embodiments, a tool or log 522, such as amonitoring tool or centralized log, which may be separate from the CI/CDpipeline may be utilized to perform the monitoring for datapoints, at510. Here, for example, a separate monitoring tool of this nature mayavoid issues with security and compliance considerations that may beassociated with tools internal to the CI/CD platform or pipeline. Insome embodiments, such a tool or log may be configured to detect andprocess only time-stamped datapoints associated with certaincheckpoints, so that none of the actual data underlying the security orcompliance concerns is ever transmitted or even known. Use of suchdisparate monitoring tool or centralized log is especially helpful withregard to certain data environments, such as those having severe dataprotection and data privacy restrictions, and/or are authorized toengage with only a limited subset of cloud-based services. Here, forexample, embodiments that involve a monitoring tool configured toprocess such persisting, time-stamped datapoints in conjunction withconfiguring the monitoring tool and the CI/CD pipeline to operate withthird parties via creation of secure or specialized data tunnels betweenthe monitoring tool and both the third-party platforms and the CI/CDpipeline overcome substantial drawbacks existing in current attempts tocoordinate or manage CI/CD dependent processes.

FIG. 6 is a flowchart illustrating one exemplary process related toperforming checkpoint and build processing associated with a CI/CDpipeline, consistent with exemplary aspects of certain embodiments ofthe present disclosure. As shown in FIG. 6, an exemplarycheckpoint/build process 600 may include a series of six initial steps(602, 604, 606, 608, 610 and 612) which are shown in one exemplarysequence in FIG. 6 for the purpose of illustration, though may becomposed of differing steps and/or performed in different order.Different sets, subsets and ordering of such steps may be performed insome implementations.

Referring to FIG. 6, an exemplary checkpoint/build process 600 maycomprise: receiving an indication of at least one first new cloudprocess to be integrated into a continuous integration/continuousdeployment (CI/CD) build of a CI/CD pipeline, at 602; identifying atleast one outside dependence for the at least one first new cloudprocess, at 604, querying an updatable tool and/or log to determine acurrent status of the at least one outside dependence, at 606;determining on a periodic or ongoing basis, whether the current statusof the at least one outside dependence identifies that the at least oneoutside dependence is incomplete so that the at least one first newcloud process would not perform as desired until the at least oneoutside dependence is complete, at 608; preventing the at least onefirst new cloud process to be integrated into the CI/CD build of theCI/CD pipeline until the current status of the at least one outsidedependence identifies that the at least one outside dependence iscomplete, at 610; and integrating the at least one first new cloudprocess into the CI/CD build of the CI/CD pipeline when the currentstatus of the at least one outside dependence identifies that the atleast one outside dependence is complete.

According to embodiments of the disclosed technology, the at least oneoutside dependence may be based on one or both of a data resourcedependence, and/or an execution of a related process. Further, in someembodiments, the updatable tool and/or log may be a centralized logconfigured to one or both of discover and monitor dependencies bycontinuously analyzing cloud processes of the CI/CD build.

With regard to the step of identifying at least one outside dependencefor the at least one first new cloud process, at 604, the at least oneoutside dependence may comprise input data that is generated outside ofone or both of: the at least one first new cloud process, and at leastone computing activity performed outside of the at least one first newcloud process. According to certain embodiments, the input data beinggenerated may include completion progress of one or more separate cloudprocesses on the one or more third-party platforms by trackingtime-stamping datapoints transmitted from and/or existent on the one ormore third-party platforms. Further, in some aspects, the outsidedependency may comprises at least one third-party platform of the one ormore third-party platforms, the at least one third-party platforminclude an entity associated with the CI/CD platform.

The overall checkpoint/build process 600 may also include one or moreadditional steps. For example, in one embodiment, the method may furthercomprise remotely monitoring the time-stamped datapoints existent on thethird-party platforms, the remote monitoring being performedcontinuously as the time-stamped datapoints are being generated forinternal use by the third-party platforms. Further, in anotherembodiment, the checkpoint/build process 600 may further compriseremotely monitoring the time-stamped datapoints existent on thethird-party platforms, the remote monitoring being performedcontinuously as the time-stamped datapoints are being generated forinternal use by the third-party platforms. According to still anotherembodiment, the checkpoint/build process 600 may further comprisepausing the CI/CD build to invoke and execute a secondary process on atleast one of the third-party platforms, recording a completion datapointregarding completion of the secondary process at the at least one of thethird-party platforms, and transmitting to the CI/CD pipeline, uponcompletion of the secondary process, a notification that the completiondatapoint has been recorded.

In some embodiments, with regard to the step of querying an updatabletool and/or centralized log to determine a current status of the atleast one outside dependence, at 606, the updatable tool or log may beconfigured to obtain, in real-time, outside dependencies associated withthe CI/CD build of the CI/CD pipeline. Further, with regard to the stepof determining whether the current status of the at least one outsidedependence, such current status may be determined by one or both of: (i)tracking datapoints transmitted from one or more third-party platformsassociated with the outside dependence, and/or (ii) tracking thedatapoints existent on the one or more third-party platforms.

According to yet another embodiment, the checkpoint/build process 600may further comprise steps such as verifying status of the secondaryprocess, e.g. via at least one computer processor performing the CI/CDbuild, by confirming or processing valid occurrences of the completiondatapoint and/or the time-stamped datapoints, and continuing, uponconfirmation of valid reporting of the completion datapoint, the CI/CDbuild based on information or feedback provided via analysis of thedatapoints of the secondary process.

FIG. 7 is a block diagram of an exemplary system and/or platform 700that may involve features of checkpoint and build processing, inaccordance with certain embodiments of the present disclosure. System700 may be configured for executing software applications, such as oneor more applications corresponding to the CI/CD platform or pipeline 218described above in connection with FIG. 2. As shown, system 700 mayinclude a client 202, such as a client computing device or one or moreother computing devices, and a network 706 connecting the various systemelements. Such client 202 or computing device(s) may be configured toexecute, among other programs, the CI/CD platform or pipeline 218, aportion of which may also reside on the client 202 as an application, at218 b. The CI/CD platform or pipeline 218 may be resident in a remote orcloud platform, or otherwise distributed among various servers and/orcomputing devices, such as a software development platform 712. System700 may further include one or more third-party platforms, computers orsystems 708, such as third-party platforms that perform the variouscloud processes initiated by the CI/CD platform or pipeline 218 throughthe cloud 224. As shown, client computing device 202, third-partyplatform 708, and development platform 712 may be communicativelycoupled by the network 706 and/or at least one cloud 224.

While only one client 202, third-party platform 708, developmentplatform 712, network 706, and cloud 224 are typically shown anddiscussed, it will be understood that system 700 may include more thanone of any of these components. More generally, the components andarrangement of the components included in system 700 may vary. Thus,system 700 may include other components that perform, or are associatedwith and/or assist in the performance of, one or more processesconsistent with the disclosed embodiments.

In some embodiments, one or more clients 202 may include computingdevices that are configured to and/or typically connect using a wirelesscommunications medium such as cell phones, smart phones, pagers, walkietalkies, radio frequency (RF) devices, infrared (IR) devices, CBs,integrated devices combining one or more of the preceding devices, orvirtually any mobile computing device, and the like. Devices associatedwith clients 202 may also be capable of connecting using a wired orwireless communication medium such as a PDA, POCKET PC, wearablecomputer, a laptop, tablet, desktop computer, a netbook, a video gamedevice, a pager, a smart phone, an ultra-mobile personal computer(UMPC), and/or any other device that is equipped to communicate over awired and/or wireless communication medium (e.g., NFC, RFID, NBIOT, 3G,4G, 5G, GSM, GPRS, WiFi, WiMax, CDMA, satellite, ZigBee, etc.). In someembodiments, one or more devices associated with clients 202 may includeand/or may run one or more applications, such as Internet browsers,mobile applications, voice calls, video games, videoconferencing, andemail, among others. In some embodiments, such devices may be configuredto receive and to send web pages, and the like. In some embodiments, anexemplary specifically programmed network or cloud tool, such as a webbrowser application, consistent with the present disclosure may beconfigured to receive and display graphics, text, multimedia, and thelike, employing virtually any web based language, including, but notlimited to Standard Generalized Markup Language (SMGL), such asHyperText Markup Language (HTML), a wireless application protocol (WAP),a Handheld Device Markup Language (HDML), such as Wireless MarkupLanguage (WML), WMLScript, XML, JavaScript, and the like. In someembodiments, such devices may be specifically programmed by either Java,.Net, QT, C, C++ and/or other suitable programming language. In someembodiments, the devices may be specifically programmed include orexecute an application to perform a variety of possible tasks, such as,without limitation, messaging functionality, browsing, searching,playing, streaming or displaying various forms of content, includinglocally stored or uploaded messages, images and/or video, and/or games.

Network(s) 706 involved with such system 700 may include and/or involvespecialized network architecture that may be based at least in part onone or more standards set by, for example, without limitation, GlobalSystem for Mobile communication (GSM) Association, the InternetEngineering Task Force (IETF), and the Worldwide Interoperability forMicrowave Access (WiMAX) forum. In some embodiments, the exemplarynetwork 105 may implement one or more of a GSM architecture, a GeneralPacket Radio Service (GPRS) architecture, a Universal MobileTelecommunications System (UMTS) architecture, and an evolution of UMTSreferred to as Long Term Evolution (LTE). In some embodiments, theexemplary network 706 may include and implement, as an alternative or inconjunction with one or more of the above, a WiMAX architecture definedby the WiMAX forum. In some embodiments and, optionally, in combinationof any embodiment described above or below, the exemplary network 706may also include, for instance, at least one of a local area network(LAN), a wide area network (WAN), the Internet, a virtual LAN (VLAN), anenterprise LAN, a layer 3 virtual private network (VPN), an enterpriseIP network, or any combination thereof. In some embodiments and,optionally, in combination of any embodiment described above or below,at least one computer network communication over the exemplary network706 may be transmitted based at least in part on one of morecommunication modes such as but not limited to: NFC, RFID, Narrow BandInternet of Things (NBIOT), ZigBee, 3G, 4G, 5G, GSM, GPRS, WiFi, WiMax,CDMA, satellite and any combination thereof. In some embodiments, theexemplary network 706 may also include mass storage, such as networkattached storage (NAS), a storage area network (SAN), a content deliverynetwork (CDN) or other forms of computer- or machine-readable media.

In some embodiments, servers associated with clients 202, developmentplatforms 712 and/or third-party platforms may be web or cloud servers(or a series of servers) running a network operating system, examples ofwhich may include but are not limited to Microsoft Windows Server,Novell NetWare, or Linux. In some embodiments, such servers may be usedfor and/or provide cloud and/or network computing.

In some embodiments, one or more such servers may be specificallyprogrammed to perform, in non-limiting example, as authenticationservers, search servers, email servers, social networking servicesservers, SMS servers, IM servers, MIMS servers, exchange servers,photo-sharing services servers, advertisement providing servers,financial/banking-related services servers, travel services servers, orany similarly suitable service-base servers for users of the CI/CDplatform or pipeline 218.

In some embodiments, various processors associated with the clients 202,platforms 708, 712, and cloud 224 may include one or moremicroprocessors, ASICs, state machines, and/or other such knowncomputing and/or processing components. In some embodiments, the systemcomponents, servers and/or processors herein may include, or may be incommunication with, media, for example computer-readable media, whichstores instructions that, when executed by the various computingcomponents, may cause relevant processors to perform one or more stepsdescribed herein. In some embodiments, examples of computer-readablemedia may include, but are not limited to, an electronic, optical,magnetic, or other storage or transmission device capable of providing aprocessor with computer-readable instructions. In some embodiments,other examples of suitable media may include, but are not limited to, afloppy disk, CD-ROM, DVD, magnetic disk, memory chip, ROM, RAM, an ASIC,a configured processor, all optical media, all magnetic tape or othermagnetic media, or any other medium from which a computer processor canread instructions. Also, various other forms of computer-readable mediamay transmit or carry instructions to a computer, including a router,private or public network, or other transmission device or channel, bothwired and wireless. In some embodiments, the instructions may comprisecode from any computer-programming language, including, for example, C,C++, Visual Basic, Java, Python, Perl, JavaScript, and etc.

In some embodiments, computing devices associated with components of thesystem 700 may also comprise a number of external or internal devicessuch as a mouse, a CD-ROM, DVD, a physical or virtual keyboard, adisplay, or other input or output devices. In some embodiments, examplesof computing devices, such as those associated with clients 202, may beany type of processor-based platforms that are connected to a network706 such as, without limitation, personal computers, digital assistants,personal digital assistants, smart phones, pagers, digital tablets,laptop computers, Internet appliances, and other processor-baseddevices. In some embodiments, such computing devices may be specificallyprogrammed with one or more application programs in accordance with oneor more principles/methodologies detailed herein.

As used in the description and in any claims, the term “based on” is notexclusive and allows for being based on additional factors notdescribed, unless the context clearly dictates otherwise. In addition,throughout the specification, the meaning of “a,” “an,” and “the”include plural references. The meaning of “in” includes “in” and “on.”

It is understood that at least one aspect/functionality of variousembodiments described herein can be performed in real-time and/ordynamically. As used herein, the term “real-time” is directed to anevent/action that can occur instantaneously or almost instantaneously intime when another event/action has occurred. For example, the “real-timeprocessing,” “real-time computation,” and “real-time execution” allpertain to the performance of a computation during the actual time thatthe related physical process (e.g., a user interacting with anapplication on a mobile device) occurs, in order that results of thecomputation can be used in guiding the physical process.

As used herein, the term “dynamically” and term “automatically,” andtheir logical and/or linguistic relatives and/or derivatives, mean thatcertain events and/or actions can be triggered and/or occur without anyhuman intervention. In some embodiments, events and/or actions inaccordance with the present disclosure can be in real-time and/or basedon a predetermined periodicity of at least one of: nanosecond, severalnanoseconds, millisecond, several milliseconds, second, several seconds,minute, several minutes, hourly, several hours, daily, several days,weekly, monthly, etc.

As used herein, the term “runtime” corresponds to any behavior that isdynamically determined during an execution of a software application orat least a portion of software application.

In some embodiments, exemplary inventive, specially programmed computingsystems/platforms with associated devices are configured to operate inthe distributed network environment, communicating with one another overone or more suitable data communication networks (e.g., the Internet,satellite, etc.) and utilizing one or more suitable data communicationprotocols/modes such as, without limitation, IPX/SPX, X.25, AX.25,AppleTalk™, TCP/IP (e.g., HTTP), Bluetooth™, near-field wirelesscommunication (NFC), RFID, Narrow Band Internet of Things (NBIOT), 3G,4G, 5G, GSM, GPRS, WiFi, WiMax, CDMA, satellite, ZigBee, and othersuitable communication modes. Various embodiments herein may includeinteractive posters that involve wireless, e.g., Bluetooth™ and/or NFC,communication aspects, as set forth in more detail further below. Insome embodiments, the NFC can represent a short-range wirelesscommunications technology in which NFC-enabled devices are “swiped,”“bumped,” “tap” or otherwise moved in close proximity to communicate. Insome embodiments, the NFC could include a set of short-range wirelesstechnologies, typically requiring a distance of 10 cm or less. In someembodiments, the NFC may operate at 13.56 MHz on ISO/IEC 18000-3 airinterface and at rates ranging from 106 kbit/s to 424 kbit/s. In someembodiments, the NFC can involve an initiator and a target; theinitiator actively generates an RF field that can power a passivetarget. In some embodiment, this can enable NFC targets to take formfactors such as, without limitation, tags, stickers, key fobs, or cardsthat do not require batteries. In some embodiments, the NFC'speer-to-peer communication can be conducted when a plurality ofNFC-enable devices (e.g., smartphones) are within close proximity ofeach other.

The material disclosed herein may be implemented in software or firmwareor a combination of them or as instructions stored on a machine-readablemedium, which may be read and executed by one or more processors. Amachine-readable medium may include any medium and/or mechanism forstoring or transmitting information in a form readable by a machine(e.g., a computing device). For example, a machine-readable medium mayinclude read only memory (ROM); random access memory (RAM); magneticdisk storage media; optical storage media; flash memory devices;electrical, optical, acoustical or other forms of propagated signals(e.g., carrier waves, infrared signals, digital signals, etc.), andothers.

As used herein, the terms “computer engine” and “engine” identify atleast one software component and/or a combination of at least onesoftware component and at least one hardware component which aredesigned/programmed/configured to manage/control other software and/orhardware components (such as the libraries, software development kits(SDKs), objects, etc.).

Examples of hardware elements may include processors, microprocessors,circuits, circuit elements (e.g., transistors, resistors, capacitors,inductors, and so forth), integrated circuits, application specificintegrated circuits (ASIC), programmable logic devices (PLD), digitalsignal processors (DSP), field programmable gate array (FPGA), logicgates, registers, semiconductor device, chips, microchips, chip sets,and so forth. In some embodiments, the one or more processors may beimplemented as a Complex Instruction Set Computer (CISC) or ReducedInstruction Set Computer (RISC) processors; x86 instruction setcompatible processors, multi-core, or any other microprocessor orcentral processing unit (CPU). In various implementations, the one ormore processors may be dual-core processor(s), dual-core mobileprocessor(s), and so forth.

Examples of software may include software components, programs,applications, computer programs, application programs, system programs,machine programs, operating system software, middleware, firmware,software modules, routines, subroutines, functions, methods, procedures,software interfaces, application program interfaces (API), instructionsets, computing code, computer code, code segments, computer codesegments, words, values, symbols, or any combination thereof.Determining whether an embodiment is implemented using hardware elementsand/or software elements may vary in accordance with any number offactors, such as desired computational rate, power levels, heattolerances, processing cycle budget, input data rates, output datarates, memory resources, data bus speeds and other design or performanceconstraints.

One or more aspects of at least one embodiment may be implemented byrepresentative instructions stored on a machine-readable medium whichrepresents various logic within the processor, which when read by amachine causes the machine to fabricate logic to perform the techniquesdescribed herein. Such representations, known as “IP cores” may bestored on a tangible, machine readable medium and supplied to variouscustomers or manufacturing facilities to load into the fabricationmachines that make the logic or processor. Of note, various embodimentsdescribed herein may, of course, be implemented using any appropriatehardware and/or computing software languages (e.g., C++, Objective-C,Swift, Java, JavaScript, Python, Perl, QT, etc.).

In some embodiments, one or more of exemplary inventive computer-basedsystems/platforms, exemplary inventive computer-based devices, and/orexemplary inventive computer-based components of the present disclosuremay include or be incorporated, partially or entirely into at least onepersonal computer (PC), laptop computer, ultra-laptop computer, tablet,touch pad, portable computer, handheld computer, palmtop computer,personal digital assistant (PDA), cellular telephone, combinationcellular telephone/PDA, television, smart device (e.g., smart phone,smart tablet or smart television), mobile internet device (MID),messaging device, data communication device, and so forth.

As used herein, term “server” should be understood to refer to a servicepoint which provides processing, database, and communication facilities.By way of example, and not limitation, the term “server” can refer to asingle, physical processor with associated communications and datastorage and database facilities, or it can refer to a networked orclustered complex of processors and associated network and storagedevices, as well as operating software and one or more database systemsand application software that support the services provided by theserver. Cloud components (e.g., FIGS. 8-9) and cloud servers areexamples.

In some embodiments, as detailed herein, one or more of exemplaryinventive computer-based systems/platforms, exemplary inventivecomputer-based devices, and/or exemplary inventive computer-basedcomponents of the present disclosure may obtain, manipulate, transfer,store, transform, generate, and/or output any digital object and/or dataunit (e.g., from inside and/or outside of a particular application) thatcan be in any suitable form such as, without limitation, a file, acontact, a task, an email, a tweet, a map, an entire application (e.g.,a calculator), etc. In some embodiments, as detailed herein, one or moreof exemplary inventive computer-based systems/platforms, exemplaryinventive computer-based devices, and/or exemplary inventivecomputer-based components of the present disclosure may be implementedacross one or more of various computer platforms such as, but notlimited to: (1) AmigaOS, AmigaOS 4; (2) FreeBSD, NetBSD, OpenBSD; (3)Linux; (4) Microsoft Windows; (5) OpenVMS; (6) OS X (Mac OS); (7) OS/2;(8) Solaris; (9) Tru64 UNIX; (10) VM; (11) Android; (12) Bada; (13)BlackBerry OS; (14) Firefox OS; (15) Ios; (16) Embedded Linux; (17) PalmOS; (18) Symbian; (19) Tizen; (20) WebOS; (21) Windows Mobile; (22)Windows Phone; (23) Adobe AIR; (24) Adobe Flash; (25) Adobe Shockwave;(26) Binary Runtime Environment for Wireless (BREW); (27) Cocoa (API);(28) Cocoa Touch; (29) Java Platforms; (30) JavaFX; (31) JavaFX Mobile;(32) Microsoft XNA; (33) Mono; (34) Mozilla Prism, XUL and XULRunner;(35) .NET Framework; (36) Silverlight; (37) Open Web Platform; (38)Oracle Database; (39) Qt; (40) SAP NetWeaver; (41) Smartface; (42) Vexi;and/OR (43) Windows Runtime.

In some embodiments, exemplary inventive computer-basedsystems/platforms, exemplary inventive computer-based devices, and/orexemplary inventive computer-based components of the present disclosuremay be configured to utilize hardwired circuitry that may be used inplace of or in combination with software instructions to implementfeatures consistent with principles of the disclosure. Thus,implementations consistent with principles of the disclosure are notlimited to any specific combination of hardware circuitry and software.For example, various embodiments may be embodied in many different waysas a software component such as, without limitation, a stand-alonesoftware package, a combination of software packages, or it may be asoftware package incorporated as a “tool” in a larger software product.

For example, exemplary software specifically programmed in accordancewith one or more principles of the present disclosure may bedownloadable from a network, for example, a website, as a stand-aloneproduct or as an add-in package for installation in an existing softwareapplication. For example, exemplary software specifically programmed inaccordance with one or more principles of the present disclosure mayalso be available as a client-server software application, or as aweb-enabled software application. For example, exemplary softwarespecifically programmed in accordance with one or more principles of thepresent disclosure may also be embodied as a software package installedon a hardware device.

In some embodiments, exemplary inventive computer-basedsystems/platforms, exemplary inventive computer-based devices, and/orexemplary inventive computer-based components of the present disclosuremay be configured to output to distinct, specifically programmedgraphical user interface implementations of the present disclosure(e.g., a desktop, a web app., etc.). In various implementations of thepresent disclosure, a final output may be displayed on a displayingscreen which may be, without limitation, a screen of a computer, ascreen of a mobile device, or the like. In various implementations, thedisplay may be a holographic display. In various implementations, thedisplay may be a transparent surface that may receive a visualprojection. Such projections may convey various forms of information,images, and/or objects. For example, such projections may be a visualoverlay for a mobile augmented reality (MAR) application.

In some embodiments, exemplary inventive computer-basedsystems/platforms, exemplary inventive computer-based devices, and/orexemplary inventive computer-based components of the present disclosuremay be configured to be utilized in various applications which mayinclude, but not limited to, gaming, mobile-device games, video chats,video conferences, live video streaming, video streaming and/oraugmented reality applications, mobile-device messenger applications,and others similarly suitable computer-device applications.

As used herein, the term “mobile electronic device,” or the like, mayrefer to any portable electronic device that may or may not be enabledwith location tracking functionality (e.g., MAC address, InternetProtocol (IP) address, or the like). For example, a mobile electronicdevice can include, but is not limited to, a mobile phone, PersonalDigital Assistant (PDA), Blackberry™, Pager, Smartphone, smart watch, orany other reasonable mobile electronic device.

As used herein, terms “proximity detection,” “locating,” “locationdata,” “location information,” and “location tracking” refer to any formof location tracking technology or locating method that can be used toprovide a location of, for example, a particular computingdevice/system/platform of the present disclosure and/or any associatedcomputing devices, based at least in part on one or more of thefollowing techniques/devices, without limitation: accelerometer(s),gyroscope(s), Global Positioning Systems (GPS); GPS accessed usingBluetooth™; GPS accessed using any reasonable form of wireless and/ornon-wireless communication; WiFi™ server location data; Bluetooth™ basedlocation data; triangulation such as, but not limited to, network basedtriangulation, WiFi™ server information based triangulation, Bluetooth™server information based triangulation; Cell Identification basedtriangulation, Enhanced Cell Identification based triangulation,Uplink-Time difference of arrival (U-TDOA) based triangulation, Time ofarrival (TOA) based triangulation, Angle of arrival (AOA) basedtriangulation; techniques and systems using a geographic coordinatesystem such as, but not limited to, longitudinal and latitudinal based,geodesic height based, Cartesian coordinates based; Radio FrequencyIdentification such as, but not limited to, Long range RFID, Short rangeRFID; using any form of RFID tag such as, but not limited to active RFIDtags, passive RFID tags, battery assisted passive RFID tags; or anyother reasonable way to determine location. For ease, at times the abovevariations are not listed or are only partially listed; this is in noway meant to be a limitation.

As used herein, terms “cloud,” “Internet cloud,” “cloud computing,”“cloud architecture,” and similar terms correspond to at least one ofthe following: (1) a large number of computers connected through areal-time communication network (e.g., Internet); (2) providing theability to run a program or application on many connected computers(e.g., physical machines, virtual machines (VMs)) at the same time; (3)network-based services, which appear to be provided by real serverhardware, and are in fact served up by virtual hardware (e.g., virtualservers), simulated by software running on one or more real machines(e.g., allowing to be moved around and scaled up (or down) on the flywithout affecting the end user).

The aforementioned examples are, of course, illustrative and notrestrictive.

As used herein, the term “user” shall have a meaning of at least oneuser. In some embodiments, the terms “user”, “subscriber”, “consumer”,or “customer” should be understood to refer to a user of an applicationor applications as described herein and/or a consumer of data suppliedby a data provider. By way of example, and not limitation, the terms“user” or “subscriber” can refer to a person who receives data providedby the data or service provider over the Internet in a browser session,or can refer to an automated software application which receives thedata and stores or processes the data.

At least some aspects of the present disclosure will now be describedwith reference to the following numbered clauses.

Clause 1. A computer-implemented method comprising:

receiving, by at least one computer processor, an indication of at leastone first new cloud process to be integrated into a continuousintegration/continuous deployment (CI/CD) build of a CI/CD pipeline;

identifying, by the at least one computer processor, at least oneoutside dependence for the at least one first new cloud process;

wherein the at least one outside dependence comprises input data that isgenerated outside of one or both of: the at least one first new cloudprocess, and at least one computing activity performed outside of the atleast one first new cloud process;

querying, by the at least one computer processor, an updatablecentralized log to determine a current status of the at least oneoutside dependence;

wherein the updatable centralized log is configured to obtain, inreal-time, outside dependencies associated with the CI/CD build of theCI/CD pipeline;

determining, by the at least one computer processor, on a periodic orongoing basis, whether the current status of the at least one outsidedependence identifies that the at least one outside dependence isincomplete so that the at least one first new cloud process would notperform as desired until the at least one outside dependence iscomplete;

wherein the current status is determined by one or both of:

-   -   (i) tracking datapoints transmitted from one or more third-party        platforms associated with the outside dependence; and    -   (ii) tracking the datapoints existent on the one or more        third-party platforms;

preventing, by the at least one computer processor, the at least onefirst new cloud process to be integrated into the CI/CD build of theCI/CD pipeline until the current status of the at least one outsidedependence identifies that the at least one outside dependence iscomplete; and

integrating, by the at least one computer processor, the at least onefirst new cloud process into the CI/CD build of the CI/CD pipeline whenthe current status of the at least one outside dependence identifiesthat the at least one outside dependence is complete.

Clause 2. The method of clause 1 or of any clause herein, wherein theinput data being generated includes completion progress of one or moreof separate cloud processes on the one or more third-party platforms bytracking time-stamping datapoints transmitted from and/or existent onthe one or more third-party platforms.Clause 3. The method of clause 2 or of any clause herein, wherein theoutside dependency comprises at least one third-party platform of theone or more third-party platforms, the at least one third-party platforminclude an entity associated with the CI/CD platform.Clause 4. The method of clause 2 or of any clause herein, furthercomprising:

remotely monitoring, by the at least one computer processor, thetime-stamped datapoints existent on the one or more third-partyplatforms, the remote monitoring being performed continuously as thetime-stamped datapoints are being generated for internal use by thethird-party platforms.

Clause 5. The method of clause 2 or of any clause herein, furthercomprising:

remotely monitoring the time-stamped datapoints existent on thethird-party platforms, the remote monitoring being performedcontinuously as the time-stamped datapoints are being generated forinternal use by the third-party platforms.

Clause 6. The method of clause 2 or of any clause herein, furthercomprising:

pausing the CI/CD build to invoke and execute a secondary process on atleast one of the third-party platforms;

recording a completion datapoint regarding completion of the secondaryprocess at the at least one of the third-party platforms; and

transmitting to the CI/CD pipeline, upon completion of the secondaryprocess, a notification that the completion datapoint has been recorded.

Clause 7. The method of clause 2 or of any clause herein, furthercomprising:

verifying status of the secondary process, by the at least one computerprocessor performing the CI/CD build, by confirming or processing validoccurrences of the completion datapoint and/or the time-stampeddatapoints; and

continuing, upon confirmation of valid reporting of the completiondatapoint, the CI/CD build based on information or feedback provided viaanalysis of the datapoints of the secondary process.

Clause 8. The method of clause 1 or of any clause herein, wherein the atleast one outside dependence is based on a data resource dependence.

Clause 9. The method of clause 1 or of any clause herein, wherein the atleast one outside dependence is based on an execution of a relatedprocess.

Clause 10. The method of clause 1 or of any clause herein, wherein thecentralized log is configured to one or both of discover and monitordependencies by continuously analyzing cloud processes of the CI/CDbuild.

Clause 11. A computer-implemented method comprising:

receiving, by at least one computer processor, an indication of at leastone first new cloud process to be integrated into a continuousintegration/continuous deployment (CI/CD) build of a CI/CD pipeline;

identifying, by the at least one computer processor, at least oneoutside dependence for the at least one first new cloud process;

wherein the at least one outside dependence comprises input data that isgenerated outside of one or both of: the at least one first new cloudprocess, and at least one computing activity performed outside of the atleast one first new cloud process;

querying, by the at least one computer processor, an updatablecentralized log to determine a current status of the at least oneoutside dependence;

wherein the updatable centralized log is configured to obtain, inreal-time, outside dependencies associated with the CI/CD build of theCI/CD pipeline;

determining, by the at least one computer processor, on a periodic orongoing basis, whether the current status of the at least one outsidedependence identifies that the at least one outside dependence isincomplete so that the at least one first new cloud process would notperform as desired until the at least one outside dependence iscomplete;

wherein the current status is determined by:

-   -   (i) tracking datapoints transmitted from one or more third-party        platforms associated with the outside dependence; and    -   (ii) tracking the datapoints existent on the one or more        third-party platforms;

preventing, by the at least one computer processor, the at least onefirst new cloud process to be integrated into the CI/CD build of theCI/CD pipeline until the current status of the at least one outsidedependence identifies that the at least one outside dependence iscomplete;

verifying the current status of the at least one outside dependence, byconfirming or processing valid occurrences of the completion datapointand/or ongoing datapoints; and

continuing, upon confirmation of valid reporting of the completiondatapoint, the CI/CD build based on information or feedback provided viaanalysis of the datapoints of the at least one outside dependence; and

integrating, by the at least one computer processor, the at least onefirst new cloud process into the CI/CD build of the CI/CD pipeline whenthe current status of the at least one outside dependence identifiesthat the at least one outside dependence is complete.

Clause 12. The method of clause 11 or of any clause herein, wherein theinput data being generated includes completion progress of one or moreof separate cloud processes on the one or more third-party platforms bytracking time-stamping datapoints transmitted from and/or existent onthe one or more third-party platforms.Clause 13. The method of clause 12 or of any clause herein, wherein theoutside dependency comprises at least one third-party platform of theone or more third-party platforms, the at least one third-party platforminclude an entity associated with the CI/CD platform.Clause 14. The method of clause 12 or of any clause herein, furthercomprising:

remotely monitoring, by the at least one computer processor, thetime-stamped datapoints existent on the third-party platforms, theremote monitoring being performed continuously as the time-stampeddatapoints are being generated for internal use by the third-partyplatforms.

Clause 15. The method of clause 12 or of any clause herein, furthercomprising: remotely monitoring the time-stamped datapoints existent onthe third-party platforms, the remote monitoring being performedcontinuously as the time-stamped datapoints are being generated forinternal use by the third-party platforms.Clause 16. The method of clause 12 or of any clause herein, furthercomprising:

pausing the CI/CD build to invoke and execute a secondary process on atleast one of the third-party platforms;

recording a completion datapoint regarding completion of the secondaryprocess at the at least one of the third-party platforms; and

transmitting to the CI/CD pipeline, upon completion of the secondaryprocess, a notification that the completion datapoint has been recorded.

Clause 17. The method of clause 12 or of any clause herein, wherein theongoing datapoints comprise time-stamped datapoints.

Clause 18. The method of clause 11 or of any clause herein, wherein theat least one outside dependence is based on a data resource dependence.

Clause 19. The method of clause 1 or of any clause herein, wherein theat least one outside dependence is based on an execution of a relatedprocess.

Clause 20. The method of clause 1 or of any clause herein, wherein thecentralized log is configured to one or both of discover and monitordependencies by continuously analyzing cloud processes of the CI/CDbuild.

Clause 21. In addition, embodiments herein may also take the form of oneor more computer readable media containing computer-executableinstructions for performing any of the processing herein, thecomputer-executable instructions being executable via one or moreprocessing components to process instructions regarding and/or otherwiseperform one or more aspects of the functionality set forth herein.Clause 22. Embodiments herein may also take the form of a systemcomprised of computing elements and/or computer-readable media that arearranged, coupled, configured, programmed and/or otherwise adapted toperform the features and functionality set forth anywhere in the presentdisclosure.

While one or more embodiments of the present disclosure have beendescribed, it is understood that these embodiments are illustrativeonly, and not restrictive, and that many modifications may becomeapparent to those of ordinary skill in the art, including that variousembodiments of the inventive methodologies, the inventivesystems/platforms, and the inventive devices described herein can beutilized in any combination with each other. Further still, the varioussteps may be carried out in any desired order (and any desired steps maybe added and/or any desired steps may be eliminated).

The invention claimed is:
 1. A computer-implemented method comprising:receiving, by at least one computer processor, an indication of at leastone first new cloud process to be integrated into a continuousintegration/continuous deployment (CI/CD) build of a CI/CD pipeline;identifying, by the at least one computer processor, at least oneoutside dependence for the at least one first new cloud process; whereinthe at least one outside dependence comprises input data that isgenerated outside of one or both of: the at least one first new cloudprocess and at least one computing activity performed outside of the atleast one first new cloud process, wherein the input data beinggenerated includes completion progress of one or more separate cloudprocesses on one or more third-party platforms monitored by trackingtime-stamped datapoints that have been generated by the one or morethird-party platforms; querying, by the at least one computer processor,an updatable centralized log to determine a current status of the atleast one outside dependence; wherein the updatable centralized log isconfigured to obtain outside dependencies associated with the CI/CDbuild of the CI/CD pipeline; and wherein the updatable centralized logdetects and processes only time-stamped datapoints associated withcertain checkpoints; determining, by the at least one computerprocessor, whether the current status of the at least one outsidedependence identifies that the at least one outside dependence isincomplete so that the at least one first new cloud process would notperform as desired until the at least one outside dependence iscomplete; and preventing, by the at least one computer processor, the atleast one first new cloud process to be integrated into the CI/CD buildof the CI/CD pipeline until the current status of the at least oneoutside dependence identifies that the at least one outside dependenceis complete.
 2. The method of claim 1 wherein the updatable centralizedlog is separately connected to both: the CI/CD pipeline via a firstsecure data tunnel, and at least one authorized third-party platform viaa second secure data tunnel.
 3. The method of claim 1 furthercomprising: integrating, by the at least one computer processor, the atleast one first new cloud process into the CI/CD build of the CI/CDpipeline when the current status of the at least one outside dependenceidentifies that the at least one outside dependence is complete.
 4. Themethod of claim 1 wherein the at least one outside dependence comprisesrecording or processing datapoint information from at least onethird-party platform of the one or more third-party platforms, whereinthe at least one third-party platform includes an entity associated withthe CI/CD platform.
 5. The method of claim 1 further comprising:remotely monitoring, by the at least one computer processor, thetime-stamped datapoints existent on the one or more third-partyplatforms, the remote monitoring being performed continuously as thetime-stamped datapoints are being generated for internal use by thethird-party platforms.
 6. The method of claim 1 further comprising:remotely monitoring the time-stamped datapoints existent on thethird-party platforms, the remote monitoring being performedcontinuously as the time-stamped datapoints are being generated forinternal use by the third-party platforms.
 7. The method of claim 1further comprising: pausing the CI/CD build to invoke and execute asecondary process on at least one of the third-party platforms;recording a completion datapoint regarding completion of the secondaryprocess at the at least one of the third-party platforms; andtransmitting to the CI/CD pipeline, upon completion of the secondaryprocess, a notification that the completion datapoint has been recorded.8. The method of claim 1 further comprising: verifying status of asecondary process, by the at least one computer processor performing theCI/CD build, by confirming or processing valid occurrences of acompletion datapoint and/or the time-stamped datapoints; and continuing,upon confirmation of valid reporting of the completion datapoint, theCI/CD build based on information or feedback provided via analysis ofdatapoints of the secondary process.
 9. The method of claim 1 whereinthe at least one outside dependence is based on one or both of a dataresource dependence and/or an execution of a related process.
 10. Themethod of claim 1 wherein the centralized log is configured to one orboth of discover and monitor dependencies by continuously analyzingcloud processes of the CI/CD build.
 11. A computer-implemented methodcomprising: receiving, by at least one computer processor, an indicationof at least one first new cloud process to be integrated into acontinuous integration/continuous deployment (CI/CD) build of a CI/CDpipeline; identifying, by the at least one computer processor, at leastone outside dependence for the at least one first new cloud process;wherein the at least one outside dependence comprises input data that isgenerated outside of one or both of: the at least one first new cloudprocess and at least one computing activity performed outside of the atleast one first new cloud process, wherein the input data beinggenerated includes completion progress of one or more separate cloudprocesses on one or more third-party platforms monitored by trackingtime-stamped datapoints that have been generated by the one or morethird-party platforms; querying, by the at least one computer processor,an updatable centralized log to determine a current status of the atleast one outside dependence; wherein the updatable centralized logdetects and processes only time-stamped datapoints associated withcertain checkpoints; determining, by the at least one computerprocessor, whether the current status of the at least one outsidedependence identifies that the at least one outside dependence isincomplete so that the at least one first new cloud process would notperform as desired until the at least one outside dependence iscomplete; preventing, by the at least one computer processor, the atleast one first new cloud process to be integrated into the C/CD buildof the CI/CD pipeline until the current status of the at least oneoutside dependence identifies that the at least one outside dependenceis complete; verifying the current status of the at least one outsidedependence, by confirming or processing valid occurrences of acompletion datapoint and/or ongoing datapoints; and continuing, uponconfirmation of valid reporting of the completion datapoint, the CI/CDbuild based on information or feedback provided via analysis of thedatapoints of the at least one outside dependence; and integrating, bythe at least one computer processor, the at least one first new cloudprocess into the CI/CD build of the CI/CD pipeline when the currentstatus of the at least one outside dependence identifies that the atleast one outside dependence is complete.
 12. The method of claim 11wherein no actual data underlying security or compliance returns is evertransmitted to or known by the CI/CD pipeline.
 13. The method of claim11 wherein the updatable centralized log is configured to obtain, inreal-time, outside dependencies associated with the CI/CD build of theCI/CD pipeline.
 14. The method of claim 11 wherein the at least oneoutside dependence comprises recording or processing datapointinformation from at least one third-party platform of the one or morethird-party platforms, wherein the at least one third-party platformincludes an entity associated with the CI/CD platform.
 15. The method ofclaim 11 further comprising: remotely monitoring, by the at least onecomputer processor, the time-stamped datapoints existent on thethird-party platforms, the remote monitoring being performedcontinuously as the time-stamped datapoints are being generated forinternal use by the third-party platforms.
 16. The method of claim 11further comprising: remotely monitoring the time-stamped datapointsexistent on the third-party platforms, the remote monitoring beingperformed continuously as the time-stamped datapoints are beinggenerated for internal use by the third-party platforms.
 17. The methodof claim 11 further comprising: pausing the CI/CD build to invoke andexecute a secondary process on at least one of the third-partyplatforms; recording a completion datapoint regarding completion of thesecondary process at the at least one of the third-party platforms; andtransmitting to the CI/CD pipeline, upon completion of the secondaryprocess, a notification that the completion datapoint has been recorded.18. The method of claim 11 wherein the ongoing datapoints comprisetime-stamped datapoints.
 19. The method of claim 11 wherein the at leastone outside dependence is based on one or both of a data resourcedependence and/or an execution of a related process.
 20. The method ofclaim 11 wherein the centralized log is configured to one or both ofdiscover and monitor dependencies by continuously analyzing cloudprocesses of the CI/CD build.